v4.3.2

Compare Source

Patch Changes

• #​427 dabba8e Thanks @​JounQin! - chore: bump unrs-resolver to v1.4.1

v4.3.1

Compare Source

Patch Changes

• #​425 2ced0ba Thanks @​JounQin! - chore: bump unrs-resolver to v1.3.3

v4.3.0

Compare Source

Minor Changes

• #​423 2fcb947 Thanks @​JounQin! - feat: throw error on malformed tsconfig reference

v4.2.7

Compare Source

Patch Changes

• aeb558f Thanks @​JounQin! - fix: add missing index.d.cts file

v4.2.6

Compare Source

Patch Changes

• #​417 c3f678b Thanks @​JounQin! - fix: require entry types, add module-sync entry

v4.2.5

Compare Source

Patch Changes

• #​410 ec59d22 Thanks @​JounQin! - fix: absolute path aliasing should not be skipped

v4.2.4

Compare Source

Patch Changes

• #​407 6b183ff Thanks @​JounQin! - chore: migrate to rebranding unrs-resolver with new targets supported:

  • i686-pc-windows-msvc
  • armv7-unknown-linux-musleabihf
  • powerpc64le-unknown-linux-gnu
  • s390x-unknown-linux-gnu

v4.2.3

Compare Source

Patch Changes

• #​402 f21bf15 Thanks @​SunsetTechuila! - fix: don't resolve not implemented node modules in bun

  is-bun-module is marked as dependency, again, for correctness, see isBunImplementedNodeModule for more details

  For Bun users: you don't need to install is-bun-module any more but bun: true option is still required if you're running without bun --bun nor run#bun enabled

v4.2.2

Compare Source

Patch Changes

• #​397 14a7688 Thanks @​JounQin! - chore: bump rspack-resolver for better P'n'P support

  Now rspack-resolver resolves pnpapi natively.

v4.2.1

Compare Source

Patch Changes

• #​394 9f11f6b Thanks @​JounQin! - fix: don't set empty configFile when no tsconfig found

• #​394 9f11f6b Thanks @​JounQin! - chore: bump rspack-resolver to v1.2.0

v4.2.0

Compare Source

Minor Changes

• #​391 c8121e5 Thanks @​JounQin! - feat: make is-bun-module as optional peer dependency

  Technically this is a BREAKING CHANGE, but considering we just raise out v4 recently and this only affects bun users, bun --bun eslint even works without this dependency, so I'd consider this as a minor change.

  So for bun users, there are three options:

  1. install is-bun-module dependency manually and use bun: true option
  2. run eslint with bun --bun eslint w/o bun: true option
  3. enable run#bun in bunfig.toml w/o bun: true option

v4.1.1

Compare Source

Patch Changes

• #​389 1b97d8a Thanks @​JounQin! - fix: should prefer module.isBuiltin when process.versions.bun available

v4.1.0

Compare Source

Minor Changes

• #​387 ef5cd10 Thanks @​JounQin! - feat: add a new bun?: boolean option for bun users - close #​386

  process.versions.bun is unavailable even with bun eslint due to its own design,
  but checking bun modules for non-bun users is incorrect behavior and just wasting time,
  so a new option is added for such case, you can still run with bun --bun eslint without this option enabled

v4.0.0

Compare Source

Major Changes

• #​368 2fd7c2e Thanks @​JounQin! - feat!: rewrite, speed up by using rspack-resolver which supports references natively under the hood

  BREAKING CHANGES:

  • drop Node 14 support, Node ^16.17.0 || >=18.6 is now required
  • alwaysTryTypes is enabled by default, you can set it as false to opt-out
  • array type of project is discouraged but still supported, single project with references are encouraged for better performance, you can enable noWarnOnMultipleProjects option to supress the warning message
  • root tsconfig.json or jsconfig.json will be used automatically if no project provided